Fix up the examples to use the new internal dataset #86
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dajmcdon
approved these changes
Jul 5, 2022
dajmcdon
deleted the
43-fix-up-the-examples-to-use-the-new-internal-dataset
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per Issue 43, fixed up the examples to use the new internal dataset... If the epiprocess datasets you are referring to are just those in the epiprocess data folder (that is,
archive_cases_dv_subset,incidence_num_outlier_example,jhu_csse_county_level_subset, andjhu_csse_daily_subset), then in the epipredict package, I only found thatjhu_csse_daily_subsetwas used in updated-example.Rmd and in the ex. of epi_recipe.R. So, in those locations I replacedjhu_csse_daily_subsetwithcase_death_rate_subset.